System for reducing payment risk, liquidity risk and systematic risk in a system wherein a payment bank host application has a filter process module for processing payments instructions, and wherein a payment bank host application applies payments risk data as input parameters to said filter process module for automated evaluation of payments instructions with respect to accounts of users such that payments instructions breaching input parameters to said filter process module are rejected back to a payments processing queue for later re-evaluation in the absence of an override instruction

ABSTRACT

A real-time, global system and method for controlling payments risk, liquidity risk and systemic risk arising between financial counterparties active in payments-based transactions. The system comprises: a plurality of User Host Applications for use by plurality of Users; a plurality of Third Party Host Applications for use by plurality of Third Parties; and a plurality of Payment Bank Host Applications for use by a plurality of Payment Banks operating a plurality of domestic payment systems. All host applications communicate via cryptographically secure sessions via private communications networks and/or the Internet global computer network. User and Payment Bank access is secured by digital certification. Each Payment Bank Host Application has a mechanism for processing payment messages, including payments instructions to be carried out in its domestic payments system on behalf of a plurality of account holders (including bank correspondents). In addition, each Payment Bank Host Application includes a filter process module for processing payments instructions, prior to being carried out by the domestic payment system. In the event of a counterparty payment failure or insolvency, the Filter Process Module enables instantaneous, automated suspension of all further payments to the counterparty in a multiplicity of chosen currencies. The reduction in payments risk and liquidity risk to predetermined tolerances reduces the likelihood of contingent defaults in the event of payment failure due to bank insolvency or other unforeseen event, and thereby reduces systemic risk to the global financial system.

BACKGROUND OF INVENTION

1. Field of Invention

The present invention relates to an improved method of and system formitigating payments risk, liquidity risk and systemic risk in thesettlement of foreign exchange transactions and many otherpayments-based transactions.

2. Brief Description of Prior Art

The foreign exchange (FX) markets in our world trade over $1 trillionworth of capital currencies daily. Economic order throughout the globalbanking system generally requires that parties engaging in such foreignexchange transactions make payments due thereunder in a timely manner toprevent default and the con-sequences associated therewith.

As shown in FIG. 1, the conventional method of making payments inconnection with foreign exchange transactions, takes place over astandard 3 day cycle. On the Trade Date, various foreign exchangetransactions are dealt either by telephone or electronic executionsystem between a User of the GPM system and a market counterparty. Thisis followed by the exchange of MT300 messages, in a prescribed industrydata format, via a global bank communications network maintained by theSociety for Worldwide Inter-bank Financial Transmissions (S.W.I.F.T).This global bank communications network, commonly referred to as theSWIFT network, is a proprietary value added network (VAN) which useelectronic data interchange (EDI) message format standards. TheInternational Standards Organization (ISO) recognizes S.W.I.F.T. as theorganization responsible for the promulgation and maintenance of thesemessage standards within the global banking industry.

Once the MT300 messages are matched in each party's back office, eachparty generates a payment instruction for the sold currency and apre-advice for the bought currency to a bank's own branch, or acorrespondent bank holding an account for the bank in a foreigncurrency. Where banks make payment using correspondent banks, theyundertake payment for their own account, whether or not they areinvolved in an underlying transaction as principal or agent of anon-bank market participant. The message types most important topayments include the MT200 for own account payments, MT202 for generalcommercial payments, and MT210 Pre-advice of expected receipt of funds.

The correspondent bank uses the S.W.I.F.T. network to confirmtransactions in an account back to the account holder. The mostimportant messages for this purpose are the MT900 advice of debit toaccount, MT910 advice of credit to account, and MT950 statement of dailyaccount activity. In short, correspondent banking is a mechanism used bybanks to effect payments in currencies other than their own.

All payment message types reference the paying bank, the account holder(if any), the receiving bank, the counterparty account holder (if any),and the unique number identifying the underlying transaction using theprescribed industry data format. Messages to correspondent banks aresent using the S.W.I.F.T. network. Messages in domestic payments systemsare sent using the network facilities and formats prescribed by theindividual domestic payment system.

Payments within domestic payment systems are currently managed b y theconstruction of a queue of payments messages for a particular day withina bank directly linked to a domestic payment system. Liquiditymanagement software is used to control the flow of payments messagesfrom the queue into the domestic payment system for clearance, tomonitor balances at the central bank, and to monitor payment conditionsvis-a-vis other directly participating banks. The liquidity managementsoftware allows payments to proceed according to the priority ofindividual payment messages and the liquidity available in the system.

Settlement Date is normally two business days after Trade Date for spottransactions in foreign exchange, and can be much later for forwardtransactions. On the Settlement Date, each branch of a bank operatingthe link to the domestic payment system for a currency, or eachcorrespondent bank acting as a nostro for other banks' payments in acurrency, will construct a payments queue containing all the messagesrequiring payment on that date.

Where the payments are to be made via a real-time gross payment systemor other system accommodating payment instructions on a real-time (asopposed to batch process) basis, the payments are released one by one assufficient liquidity in the clearing account of the bank permits.Liquidity management software is used by banks connecting to thesesystems to keep track of the balance in the clearing account within thepayments system and release payments as liquidity permits. Also, suchsoftware will generally ensure that sufficient balance or credit existsin the account of the account holder to cover the payment. Such softwareshall hereinafter be described as “liquidity/payments manager.” Paymentsmade from the queue reduce the balance, while payments received fromother banks in the system increase the balance. The process continuesuntil all payments on the queue are sent.

Banks acknowledge payments and receipts to their correspondent bankingaccount holders using the S.W.I.F.T. network, and to non-bank accountholders using various methods. For correspondent banks, an MT900 is sentfollowing debit of a payment from a client's account. An MT910 is sentfollowing credit of a received payment to a client account. At the endof the day, an MT950 statement of account activity is sent to confirmevery debit and credit through the account during the day, and theopening and closing balances, using an industry standard data format.

The Reconciliation Date is normally the day following the Payment Date.Institutions active in the foreign exchange markets typically take allthe MT950 statements from all branches and correspondent banks acting ontheir behalf for settlement, and provide these statements as inputs to abatch process for reconciliation. This process determines whether foreach payment made in respect of a trade, whether a counterpayment wasduly received as expected. If payment has been made, but nocounterpayment received, then the party is at risk for the gross amountof the payment as an unsecured creditor of the counterparty. Anexceptions report is generated as a result of the reconciliation batchprocess, which is used for querying missed payments with counterparties,generally by telephone. Only after a query (often made difficult bygeographical distance and time zone differences) can a decision be madeabout the credit-worthiness or potential default of a counterparty. As aresult it can be two or three days following missed payments before acounterparty is declared in default and further payments are suspended.As a result of this process overall, the risk to a foreign exchangemarket participant, arising because payments are typically instructed ona transactional basis (as obligations are incurred) and are processedindependent of other transactions which would result in expectedreceipts, may be as much as three days gross value of payments to acounterparty. This risk is known as “payments risk”.

Payments risk may well exceed the capital of a bank or other financialinstitution, raising a potential that a counterparty failure could causetheir own insolvency, arising from the difficulty that financialinstitutions are likely to have raising funding rapidly to cover ashortfall should expected receipts fail to materialize on the paymentdate. This risk is known as “liquidity risk”.

Liquidity risk, in turn, may perpetuate a systemic impact throughout thechain of counterparties active in the financial markets, arising frompayment failure due to liquidity problems, through a chain ofco-dependent payments transactions. This risk is known as “systemicrisk” and is a principal concern of central bankers and supervisors inoverseeing the strength of capital markets. Payments risk, liquidityrisk, and systemic risk associated with participation in paymentssystems are summarised in the table of FIG. 2.

Cross-border payments risk in the foreign exchange markets has beenexacerbated by recent trends in the markets. Many smaller participantsnow trade directly in the markets through electronic foreign exchangetrading systems. The past five years have seen the market share of thetop dealing banks fall from approximately 60 percent of the market toless than 40 percent of the market, demonstrating their displacement bymore active smaller institutions. These smaller institutions tend tohave lower credit ratings, and so present higher levels of payments riskto their counterparties. Additionally, there has been a shift towardincreased trading volumes in the currencies of emerging economies. Thesecurrencies are generally less liquid and more volatile, particularly inconditions of general market uncertainty, and so present higherliquidity risk and systemic risk in the event of a financial failure.

In addition, there has been a movement toward more rapid settlement oftransactions, with some transactions now settling on the same day astrading or the next day, as opposed to the customary two days followingtrade date. The shorter settlement times put pressure on banks involvedin payments as they increase uncertainty as to liquidity, and are ofteninconsistent with existing systems for trade processing andreconciliation.

Even in a single currency, there is a more general payment riskassociated with banks and commercial entities making payments to partieswho are expected to make unrelated payments back on the same day.Currently, all general commercial payments on behalf of account holdersare made irrespective of whether expected receipts actually occur. Theresult is that financial market participants and others incur creditrisk on their payments which can result in large losses in the event ofthe counterparty's insolvency. This risk is possibly increasing asfinancial institutions are disintermediated from financial markets, withmany institutions dealing directly with one another on a regular basisthrough electronic communications networks (ECN) and otherwise.

Hitherto, a number of prior art systems and methods have been proposedfor mitigating or managing the various types of risk associated withmaking payments in connection with foreign exchange transactions in ourglobal financial capital market system.

One proposed method of managing payment risk involves the “contractualnetting” of payment flows, whereby parties agree to net all paymentobligations for any given date and only effect net payments to oneanother.

Contractual netting requires that both parties sign an enforceable legalagreement to net their obligations, that the parties agree daily thespecific amounts of the payment flows in settlement of transactions, andthat the parties maintain systems for the reconciliation of paymentsagainst transactions to ensure that underlying transactions have beensettled. Supervisors generally require independent legal opinionssupporting netting enforceability before conferring any benefit of riskreduction for capital adequacy purposes. In consequence of itscomplexity and legal uncertainty in many countries, contractual paymentsnetting embraces only one-quarter of transactions in foreign exchangemarkets.

In connection with the above method of risk management, a systemreferred to as FXNET exists for the calculation of bilateral nettingexposures and net payment amounts in traded currencies for itsparticipants. This system is designed to reduce the operationalcomplexity of bilateral netting on a daily basis as between its users.It has less than 100 bank users.

In addition, two other systems have been proposed for providingmulti-lateral netting, or clearing house, operations to the foreignexchange markets. The first system is the MultiNet system which neverbecame operational, and was abandoned in late 1996. The second system isthe Exchange Clearing House (ECHO) which was operational for severalyears, but operations were suspended in 1998 because they were deemeduneconomic.

CLS Bank has proposed an alternative method of managing risk inconnection with foreign exchange transaction payment systems. Thismethod involves developing a clearinghouse which seeks to provide atiered system for clearing foreign exchange settlements, ending withvalue-for-value settlement of foreign exchange transactions through theagency of a special purpose bank with accounts at participating centralbanks. CLS Bank's clearinghouse is only effective for transactionswholly in the currencies admitted to the system (i.e. 7 currencies areproposed for initial operations), only market participants joining theCLS system or clearing through participants, and only for foreignexchange settlements. The CLS system requires substantial investment andchanges to existing systems for reporting and matching of transactions,and for payment and liquidity management among participants. Even if CLSBank were to settle all eligible foreign exchange trades for all its 60shareholder banks, this would only address the risk on 27 percent offoreign exchange market transactions.

In summary, prior art methods of and methods for managing risk inconnection with FX and other payments transactions throughout the worldsuffer from the following shortcomings and drawbacks: they requireagreement of the transaction counterparty; they do not extend tonon-bank counterparties; they are complex and difficult to implement;and they do not adequately enable a typical foreign exchange or othermarket participant to control the risk arising in respect of theplurality of its counterparties, currencies and payment types.

Consequently, there is a great need in the art to provide an improvedmethod of and system for mitigating risk associated with participationin payments systems involved in settling foreign exchange and otherfinancial transactions.

OBJECTS OF THE PRESENT INVENTION

Accordingly, a primary object of the present invention is to provide aglobal computer-based method of and system for mitigating risk arisingin connection with foreign exchange settlements and other paymentsbetween financial market participants, while avoiding the shortcomingsand drawbacks of prior art methodologies.

Another object of the present invention is to provide such a system,wherein the control of payments risk is efficiently enabled in as manycurrencies as may be interoperable with such a system.

Another object of the present invention is to provide such system in theform of a real-time Internet-based method of and system for controllingpayment flows in a way that reduces payment risk between counterparties,both within a single domestic payment system and globally through amulti-currency implementation.

Another object of the present invention is to provide such a system asenables the control of payments risk arising for an account holderwithin a single currency, as well as cross-border payments risk arisingfrom payments in a plurality of currencies.

A further object of the present invention is to provide a computer-basedpayment risk management system to enable control of payments risk forall payment flows, whether arising from foreign exchange transactions orother payment types.

Another object of the present invention is to provide such a system asenables a participant to unilaterally control his risk vis-a-vis aparticular payments counterparty, without the necessity for thecounterparty's agreement or cooperation.

Another object of the present invention is to provide such a system asallows participants to more efficiently manage their current business,reduce overhead, improve returns on capital, and support new businesswith counterparties by reducing payments risk and enabling moreefficient liquidity and credit risk management.

Another object of the present invention is to provide such acomputer-based system and software that can readily be used by allforeign exchange market participants, from money-center banks tocorporate end-users worldwide.

A further object of the present invention is to provide a computer-basedpayments risk reduction system which does not require substantial changeto the conventional market trading, confirmation, matching and clearingpractices in the foreign exchange market or payments clearing andsettlement practices in correspondent banking.

A further object of the present invention is to enable each financialinstitution or corporate hierarchy to determine the optimal allocationof system access, such that any individual branch, subsidiary, companyor other legal or organizational entity can have separate access.

A further object of the present invention is to provide a computer-basedsystem in which separate accounts can be flexibly aggregated ordisaggregated by participants for risk management and reporting purposesto promote effective oversight of group or individual participant use ofthe system.

A further object of the present invention is to provide a computer-basedsystem in which separate counterparty accounts can be flexiblyaggregated or disaggregated for risk management purposes and reportingpurposes according to participant assessment of risk correlation betweenaffiliated, connected or similar counterparties.

A further object of the present invention is to provide a computer-basedsystem in which payment flows with a counterparty or counterparties in aplurality of currencies can be flexibly aggregated for risk managementpurposes and reporting purposes.

A further object of the present invention is to provide a computer-basedpayments risk reduction system that is consistent with and complementaryto the existing network for inter-bank financial communications(S.W.I.F.T.) and the internet protocol networks increasingly used byfinancial institutions.

A further object of the present invention is to provide a computer-basedpayments risk reduction system which does not require informationdetails regarding the underlying transactions on which the system actsto reduce payments risk.

A further object of the present invention is to provide a computer-basedpayments risk reduction system which allows individual participants todetermine unilaterally their tolerances for payment risk according tocounterparty, currency and payment type.

A further object of the present invention is to provide such a system inwhich participants can view, enter and alter their risk parameters forcounterparties, currencies and payment types on a real-time basis.

A further object of the present invention is to provide such a system inwhich the payment parameters of account holders can be entered into thedatabase of the system by way of screen-entry, batch-entry orintegration with internal systems processes.

A further object of the present invention is to provide such a system inwhich payments risk can be controlled in an automated manner throughintegration with the existing payments systems operating within paymentbanks directly connected to domestic payments systems.

A further object of the present invention is to provide such a system asenables payment banks to integrate the system host application in amodular fashion in connection with their participation in domesticpayment systems with a high degree of openness, flexibility andinteroperability.

A further object of the present invention is to provide a quicker andeasier means for monitoring payment flows and reporting exceptionsituations which may indicate a counterparty payment failure.

A further object of the present invention is to provide a computer-basedsystem for a payment bank to notify account holders of payment problemsintra-day, enabling them to take such actions as will forestall anyadverse impact on liquidity in that and other currencies.

A further object of the present invention is to provide a quicker andeasier means for inquiries into exception situations betweenparticipants, counterparties and payment banks, facilitating earliercorrective action or remedial action as appropriate.

A further object of the present invention is to provide a computer-basedsystem for account holders to notify payment banks in real-time of theirwish to suspend any further payments to an individual counterparty.

A further object of the present invention is to provide thecomputer-based system capability within a payment bank to efficientlyand effectively suspend any further payments to a particularcounterparty on behalf of an account holder, following receipt of arequest from an account holder to do so.

A further object of the present invention is to provide a computer-basedsystem enabling automated calculation of global risk positions based onpayments activities in multiple payments systems.

A further object of the present invention is to provide a computer-basedsystem which integrates the advantages of Web-based informationmanagement, browser interfaces, application-to-application datainterchange, object-oriented programming and open systems technologiesto deliver improved flexibility, extensibility, modularity,interoperability and other information management advantages inconnection with payments risk management.

A further object of the present invention is to reduce or eliminate thesystemic risk that a payment failure by one market counterparty may leadto failure of contingent payments down a chain of interrelated paymentstransactions, and thereby threaten the liquidity and integrity ofpayment and banking systems within a single market or globally.

A further object of the present invention is to provide such a system,in which a participant's payments liquidity is optimally used to meetpayment obligations in an automated manner.

A further object of the present invention is to provide such as systemin which liquidity management software is employed to addresscross-border payment risk or payment risk arising on the level of theindividual account holder within a participating bank.

A further object of the present invention is to provide such a system inwhich payment instructions can be processed very rapidly afternegotiation of the underlying transaction without compromising paymentsrisk mitigation.

A further object of the present invention is to provide such a system asenables access via a plurality of internet protocol networks and aplurality of computing devices, and flexibility in the use andconfiguration of access software to meet individual functionalrequirements and capacity to support technological integration.

A further object of the present invention is to provide such a system inwhich many-to-many data processing rationalizes the flows of informationbetween host applications located anywhere around the globe (in bothdeveloped and emerging markets) without the prejudices and disadvantagesarising from geographical dispersion.

A further object of the present invention is to provide such a system inwhich payment risk parameters and other data entered into the system areautomatically interpreted by rule-based interpretation procedures as toprocessing requirements.

A further object of the present invention is to provide such a system inwhich account holder payment parameters are managed on a database andcommunicated as operable parameters for payments processing by hostapplications in payment banks.

A further object of the present invention is to provide a system whichuses or interoperates with industry standard data formats for thecapture and transmission of like data to enable efficient interface withpre-existing banking applications and systems.

A further object of the present invention is to provide a system whichprovides appropriate security and integrity for the transmission of alldata across its network via cryptographically secure sessions anddigital certification of host application subscribers.

These and other objects of the present invention will become apparenthereinafter and in the claims to Invention.

SUMMARY OF INVENTION

According to one aspect of the present invention, a Global PaymentsManagement (GPM) system and method are provided for the purpose of tyingtogether Third Parties, Users and Payment Banks sites (in the UnitedStates, Europe, Asia and other locations throughout the world) via aglobal communication network (e.g., interconnected internet protocolnetworks and a virtual private network) to enable Third Parties andUsers to communicate payments risk parameters and other instructions toPayment Banks making and receiving payments on their behalf, tofacilitate real-time communications system-wide, and to provide moretimely and better quality information on payments risk management.

In order to support Third Parties, Users and Payment Banks located indifferent time zones, the GPM System preferably is available 24 hours aday and seven days a week. Such high availability allows Third Parties,Users and Payment Banks to participate in the system in a substantiallyequal manner, overcoming the disadvantages of remote location inherentin foreign exchange trading and settlement. The system takes advantageof advances in Internet Protocol (IP) networks, Web-based programmingand electronic data interchange (EDI) techniques to ensure itscompatibility with the plurality of existing operating systems, legacysoftware and participants' levels of technological sophistication. Thesystem can be used by all market participants, large and small, who wishto reduce the payment risk exposures arising from their participation inforeign exchange markets and/or improve the risk and liquiditymanagement associated with their domestic and international paymentsgenerally.

Third Parties potentially include all financial and commercial entitiesinvolved in substantial wholesale payment flows as account holders witha User bank or non-bank financial institution.

Users potentially include all banks and non-bank financial institutionsinstructing payment on their own behalf or as correspondent on behalf ofThird Parties, and all financial and commercial entities as accountholders in a domestic payment system. Third Parties in a cross-bordercontext may simultaneously be Users in a domestic context.

Payment Banks potentially include all banks and non-bank financialinstitutions directly linked to a domestic payment system. Users maysimultaneously be Payment Banks.

Counterparties potentially include all market participants who transactwith Users and Third Parties to create payment obligations. The GPMSystem of the present invention will enable Users and Third Parties toflexibly structure identification of counterparties to aggregate ordisaggregate affiliates within a corporate group or branches of afinancial institution.

The GPM System of the illustrated embodiment supports the followingfunctionalities: Third Party and User host applications for screen,batch and automated entry of payment risk parameters by currency,counterparty and payment type; a core system host application forautomatic rule-based sorting of parameters according to Payment Bankacting on behalf of Users for payments in a particular currency and/orto a particular counterparty; communication of parameters to the PaymentBank host application controlling payment flows to the domestic paymentsystem(s); automatic rule-based filtering within the Payment Bank hostapplication of payment messages against User-specified payments riskparameters to ensure continuing compliance with parameters; real-timenotification of exception conditions from the Payment Bank to the User(e.g., to indicate counterparty payment difficulties); real-timecommunications messaging between Third Parties, Users and Payment Banksto facilitate inquiry into and resolution of exception conditions;ability for the Payment Bank to manually override the Payment Banksoftware to enable a payment to proceed notwithstanding non-compliancewith parameters; ability for a User to instruct the Payment Bank tosuspend any further payments to a particular counterparty; ability forPayment Bank host application to stop any further payments to anycounterparty; ability to flexibly generate a variety of reportsperiodically or on request according to the requirements of ThirdParties, Users and Payment Banks; secure, reliable and encryptedcommunications; and accommodation of multiple Third Parties, multipleUsers, and multiple Payment Banks at multiple geographical locations.

In accordance with the illustrative embodiment of the present invention,Third Parties have pre-existing account relationships with Users suchthat Users transact payments on their behalf. Users acting on behalf ofThird Parties are institutions possessing a Bank Identifier Code (BIC)as published by S.W.I.F.T., a universal standard identification methodrecognised by the ISO. The BIC is a unique address which, intelecommunication messages, identifies precisely the financialinstitution involved in financial transactions.

Users have pre-existing account relationships with Payment Banks suchthat Payment Banks transact payments on their behalf. Banks or branchesacting as Payment Banks for a User are identified by their BIC.

The GPM System has five principal component parts: a GPM Network, aThird Party Host Application, a User Host Application, a GPM Core Systemand a Payment Bank Host Application. The GPM Network is a network ofcommercial and privately operated IP networks interlinked to the GPMVirtual Private Network (GPM/VPN) using routers. The GPM/VPN, operatingwith controlled access, cryptography and firewalls, will ensure superiorsecurity, integrity and resiliency for the GPM System.

The customer account structure within the GPM System is deliberatelyflexible as to organization and number of customer accounts for anygiven corporate entity or affiliated group. Banks, for example, maychoose to assign each branch dealing in the markets for its own accounta separate User status within the GPM System, or alternatively may wishto centralise control in a single branch through assigning otherbranches the status of Third Parties. Corporate treasuries may similarlydisaggregate corporate divisions as Users with their own accounts, oraggregate them as Third Parties under a single User account. Regardlessof account structure, the GPM System enables accounts to be linkedtogether for reporting purposes in flexible hierarchies of User andThird Party accounts, according to whatever configuration a User mayrequire.

Throughout the preferred embodiment of the GPM System, its softwarecomponents are created using the Java™ programming language, its dataformat protocol expressed in the extensible Mark-up Language (XML), andits human-machine interfaces realized using Web (http) browserinterfaces enabling human users to interact with the system. TheWeb-based architecture of the GPM system has significant advantages interms of flexibility, openness, interoperability and maintenance, inparticular enabling flexible publication of information and softwareupgrades, interoperability with a wide variety of pre-existingtechnology platforms, on-line application interaction and communicationssystem-wide, and other processes related to Web-based and distributedcomputing.

Preferably, network interconnection between Third Parties and Users willbe jointly determinated. Third Parties communicate their risk parametersand other payment-related information to Users. Only Users can pass riskparameters or payments-related information through to Payment Banks, asonly the account holder (the User) can properly instruct a bank (thePayment Bank) as to actions affecting an account.

The Third Party Host Application is realized as software provided toThird Parties as clients of Users at multiple sites located globally.The software components of the GPM system, including the Third PartyHost Application, can be downloaded from a Website on the World Wide Web(WWW) with or without payment of a fee. Various instances of the ThirdParty Host Application may be available to cater for differences inlanguage, financial markets activity, and relative technological andfinancial sophistication of the plurality of Third Parties. The HostApplication enables a Third Party to request that a User bank generateprocesses in the GPM System reflecting the expressed preferences of theThird Party with respect to risk management, messaging and reporting.Whether the User is required to implement these requests through the GPMSystem will be a matter for joint agreement between the User and theThird Party. Third Party access to Users and the GPM System may bethrough manual input, batch input or automatedapplication-to-application data interchange. Preferably, the Third PartyHost Application also supports inquiries, reports and messaging similarto the User Host Application.

The User Host Application is realized as software provided to Users ofthe GPM system at multiple sites located globally. Various instances ofthe User Host Application will be available, to cater for differences inlanguage, financial markets activity, and relative technological andfinancial sophistication of the plurality of Users big and small. At thesimplest instance in the illustrated embodiment, a browser interface tothe User Host Application will enable any small User with the capabilityof launching a commercially available browser to access, manually inputto and use the GPM System. For those Users with moderate complexity(perhaps regular participants in the foreign exchange markets but notdealers themselves) an instance of the User Host Application willadditionally provide facilities for file upload from commerciallyavailable spreadsheet programs using commercially available software fordata translation. At the most sophisticated level, for Users who aredealers in the foreign exchange markets or commercial or investmentbanks, the User Host Application can integrate with pre-existingtransactions systems in the middle and back office using data mappingand electronic data interchange functionalities.

On a periodic (usually daily) or real-time basis, the Users of the GPMSystem determine their tolerance for loss in respect of eachcounterparty in each currency as payment risk parameters for GPMprocessing, either on their own account or on behalf of Third Parties.The basic parameters are a net payment limit (which may be set to zero)and a debit cap (which may be set to zero). Users may alter riskparameters at any time. GPM Users will have the option of applying riskparameters to counterparty payments according to message type, so thatthe GPM System can address payment risk either for own account transfers(MT200) and commercial payments (MT202) in a cross-border context, andother categories of payments arising in domestic payment systems.

In the illustrative embodiment of the present invention, the Third Partyand User Host Application access the system using commercially availableWeb browsers supporting eXtensible Mark-up Language (XML). The XML dataprotocol is extremely useful as it is capable of support forhuman-to-machine and machine-to-machine interactions. This providestremendous flexibility for human interaction with the GPM System as theThird Party or User Host Application can therefore be accessed from anyworkstation or other device capable of launching a browser and accessingthe installed software via telecommunications. This has advantagesparticularly for banks or companies with geographically dispersedoperations, as various offices can access a single instance of the ThirdParty or User Host Application installed at a central site.Alternatively, an executive travelling from his office may still be ableto access the Third Party or User Host Application viatelecommunications link into the office's internal systems.

The “risk parameter” data files are transmitted to the GPM system via IPnetworks interlinked by routers to a GPM Virtual Private Network(GPM/VPN). The GPM/VPN provides improved facilities for ensuring thesecurity, integrity and resiliency of the telecommunications network.The network structure offers flexibility as well. as the GPM/VPN can beinterlinked via routers to commercially available internet networks(e.g., ATT, Sprint, BTSyntegra), virtual private networks owned by banksor consortia (e.g., VPNs operated by Reuters, Bloomberg, Equant, IBM),and even the Internet.

Once the GPM has received risk parameters or other messages from a User,the GPM Core System stores the input in the Data Server and processesthe input in the Process Server. Data changes and messages will besorted according to recipient using rules-based processing acting on thedata fields in the files and messages. New data files are generatedcontaining risk parameters for action by a single Payment Bank. Thesefiles are then published to Payment Bank Host Application installed as amodule at Payment Banks acting for the User. Messages are sorted androuted to the appropriate recipient.

Risk parameters are used by the Payment Bank Host Application in theFilter Process Module of the present invention. The Filter ProcessModule is designed to interoperate with an existing liquidity/paymentsmanager to filter payments flowing between the payment queue maintainedon the bank's existing internal systems and the external domesticpayment system(s) to ensure that all payments made on behalf of a Usercomply with the User's risk parameters. The fundamental mechanism is thecomparison of the payment amount in a payment instruction against anavailable balance calculated for the recipient counterparty. Where thepayment amount is within the available balance, the payment instructionis allowed to proceed. Where the payment amount is greater than theavailable balance, the payment instruction is rejected back to thepayment queue for later reassessment. As payments from a counterpartyare received, the available balance rises; as payments are made theavailable balance falls. The Payment Bank Host Application acts as theshuttle on a loom, ensuring payments flow back and forth between twocounterparties in balanced measure. The Payment Bank may override therisk parameters with a manual instruction, in its discretion or at therequest of a User. This feature may facilitate liquidity in a paymentsystem, particularly one that is illiquid or highly concentrated, wherefailure by one bank in the system to make a payment impedes the abilityof another bank in the system to make a contingent payment (i.e., abottleneck).

The Payment Bank Host Application enables the Payment Bank to monitorthe flows of payments to and from User accounts in respect of individualcounterparties, allowing them to detect an imbalance which impedesfurther payments in accordance with User parameters. The GPM Systemenables the Payment Bank to notify a User in real-time should asustained imbalance in payments received from a counterparty result in afailure to make payments to the counterparty. Such an event may indicateliquidity or payment difficulties at the counterparty, and wouldnormally be the subject of inquiry by the User, and perhaps action tosuspend further payments to the counterparty in that and othercurrencies, and to raise any consequent liquidity shortfall which mightimpact systemic payment flows.

The Filter Process Module of the present invention will have theimportant capability of automatically responding to a User instructionto suspend all payments to a particular counterparty, stopping allfurther payments as they are submitted for checking during paymentsprocessing. Alternatively, the Payment Bank may manually instruct theFilter Process Module via the Payment Bank Host Application to stop allfurther payments to a particular counterparty, where it deems suchaction appropriate (e.g., where it has been notified of an insolvency).This mechanism provides a very significant improvement on the ability tointervene to stop payments in the event of a known insolvency or othercondition of similar concern.

The GPM System facilitates broad range of communications betweenparticipants in connection with payments management. Some inquiries willbe handled by the system on an automated basis. For example, ThirdParties (via Users) and Users may request detailed or summaryinformation about counterparties or currencies. Third Party and Userrequests will be routed via the GPM Network to the Payment Bank(s)acting on their behalf to the Payment Bank Host Application. The PaymentBank Host Application has the capacity to automatically fulfill inquiryrequirements according to data on the day's activities, and will thensend the inquiry response back through the GPM Network to the initiatingUser or Third Party.

Real-time messaging will be available between all GPM Systemparticipants. A User who is alerted by a Payment Bank of a sustainedpayment failure may then make on-line inquiry to the counterparty, wherethe counterparty is also a User. The counterparty can then make inquiryto his own Payment Bank to request clarification or resolution of thepayments problem.

Reports are available on a periodic or on-demand basis for all GPMNetwork participants. All Third Party, User and Payment Bank HostApplication are capable of generating flexible, parameterized reports,according to the requirements of the request. Reports can contain dataabout counterparties currencies, payment types and metrics of paymentrisk reduction calculated by the GPM Core System. The GPM Core Systemcan also calculate performance metrics such as the efficiency ofpayments and liquidity management, and other relevant statistics.

Other advantages of the present invention will become apparent hereinafter.

BRIEF DESCRIPTION OF THF DRAWINGS

For a more complete understanding of the Objects of the Invention, thefollowing Detailed Description of the Illustrative Embodiments should beread in conjunction with the accompanying Drawings, wherein:

FIG. 1 is a tabular schematic of the prior art three-day process forgross (transaction by transaction) foreign exchange settlements;

FIG. 2 is a table listing the different types of risks arising inpayments systems;

FIG. 3 is a schematic diagram of the network for communications in theGPM System of the present invention, shown realized as a plurality ofThird Party and User client workstations, applications interfaces andWeb applications in operable communications with one another through aWeb-enabled architecture, embracing both existing internet protocolnetworks widely in use in the financial markets and interlinked to avirtual private network for communications between the GPM Core Systemand the Payment Bank Host Application installed within Payment Banksystems;

FIG. 4 is a schematic diagram of the GPM Core System of the presentinvention, shown realized as a plurality of client-server workstationsin operable communications with each other through a wide area network(WAN) and showing various processes carried out on the client-serverworkstations of the system, the whole being connected by a plurality ofinternet protocol networks to Users and by a virtual private network(VPN) to Payment Banks;

FIG. 5 is a schematic of the digital certificate issuance and usageprocess;

FIG. 6 is a tabular schematic of the three-day process for foreignexchange settlements incorporating the Granular Payment Managementprocesses:

FIG. 7 is a schematic diagram of the flow of risk parameters, suspendinstructions and messaging through the GPM System of the presentinvention;

FIG. 8 is a schematic representation of the controlled and sequencedflows of payments between two Users via their Payment Banks;

FIG. 9A 1 is a schematic representation of Risk Parameter InstructionProcess in the GPM System of the present invention;

FIG. 9A 2 is a tabular schematic of a message format capable ofinstructing payment risk parameters to a Payment Bank;

FIG. 9B is a listing of the Risk Parameters required for use in theFilter Process of the Payment Bank Host Application;

FIG. 9C is a schematic representation of the modular nature of theFilter Process in the Payment Bank Host Application, acting as anadjunct to existing liquidity/payments management software operatingwithin banks directly interfacing to domestic payment systems;

FIG. 9D 1 is a step-by-step textual description of the Filter Process ofFIG. 9C;

FIG. 9D 2 is a schematic representation of the Filter Process of FIG.9C;

FIG. 9E 1 is a step-by-step textual description of the method forcalculating the Available Balance parameter required for the FilterProcess of FIG. 9C;

FIG. 9E 2 is a schematic representation of the method for calculatingthe Available Balance parameter required for the Filter Process; of FIG.9C FIG. 9F 1 is a schematic representation of the instruction andconfirmation process involved in suspending payment;

FIG. 9F 2 is a tabular schematic of a message format capable ofinstructing suspension of payments in respect of a selected CounterpartyFIG. 3 is a tabular schematic of the process for gross foreign exchangesettlements using the GPM System of the present invention;

FIG. 9F 3 is a step-by-step textual description of the method forsuspending payments, as originated in the Third Party or User HostApplication, processed through the GPM Core System, and implemented viathe Filter Process in the Payment Bank Host Application; and

FIG. 10 is a graphical representation demonstrating the advantages ofthe present invention for reducing and controlling levels of paymentrisk as between two counterparties both using the GPM System of thepresent invention.

DETAILED DESCRIPTION OF THE BEST MODE EMBODIMENT OF THF PRESENTINVENTION

Referring to the figures of FIG. 3 through 10 the best mode embodimentof the present invention will be described in detail below, wherein likeelements and structures will be indicated using like reference numerals.

In general, the Granular Payments Management (GPM) system of the presentinvention may be realized in a variety of ways depending on the enablingtechnology available at the time of realization and particularapplication requirements at hand.

As shown in FIG. 3, the GPM System of the illustrative embodiment isshown comprising a Web-based network of client-server workstations onwhich Web-server and Web-linked interface applications are supported,and Third Party, User and Payment Bank Host Applications, and spatiallydistributed about the planet Earth in order to provide real-time serviceto the diverse Third Parties, Users and Payment Banks that the system isdesigned to serve. It is understood, however, that the system can berealized in other ways.

As shown in FIG. 3, the GPM System involves a network of connected ThirdParty Host Applications, User Host Applications, Payment Bank HostApplications and the GPM Core System running on the Web-basedclient-server information network. The schematic for the illustrativeembodiment demonstrates the flexibility of the network forinterconnecting those involved in payment flows. Third Party (4) andUser (1) access mechanisms include: a plurality of proprietary networkaccess workstations, personal computers, internally networked clientsaccessing servers, application-to-application integration with backoffice transaction processing systems, and other arrangements promotingease of access and flexible use.

The Third Party host application (4) will connect to a User hostapplication (1) via network arrangements agreed between them and usinginternet protocol communications networks, whether private, commercialor the Internet. The Third Party Host Application will be capable ofautomated interoperability with the User Host Application to set riskmanagement parameters for processing of payments on behalf of ThirdParties where the User acts as correspondent, to generate suspendinstructions when necessary, and to define requirements for messaging,inquiries or reports via the GPM Network.

Users will be interconnected to the GPM Virtual Private Network(GPM/VPN) (6.1) via routers (6.3) and a variety of internet protocolnetworks (6.2), likely to include the private and commercial networksmost widely used in the financial sector, but potentially including theInternet.

The VPN interconnects via a router (6.3) to the GPM Core System (2).

In the illustrative embodiment, the GPM Core System processes the datareceived from the plurality of Users into data to be published to theplurality of Payment Banks. The GPM Core System communicates via the VPNto the Payment Bank Host Application (3) installed as a modularcomponent within the payment systems of Payment Banks. The Payment Banksthen further interface to the domestic payment system(s) for eachcurrency (5) using the established present interfaces and networks.

An important feature of the present invention as depicted in theillustrative embodiment is the capability for many-to-many publishing ofpayments data from and to diverse data formats as used within theheterogeneous plurality of Third Parties, Users and Payment Banks. Theuse open software applications capable of integration with any computingplatform, and eXtensible Mark-up Language (XML) as the data formatprotocol in the Third Party Host Application, User Host Application andPayment Bank Host Application, will promote the interoperability of theGPM System with legacy systems and applications within Third Parties,Users and Payment Banks.

XML has several critical advantages. First, XML is both human-readableusing browsers and XSL stylesheets, and machine-readable forapplication-to-application automated processing. Second, it is an openstandard capable of ready translation via data mapping into otherexisting data standards (including S.W.I.F.T. and other EDI standards)using commercially available translation methodologies. This willpromote interoperability with existing risk management, payment andother computerised and automated systems within Third Parties, Users andPayment Banks. Third, commercially available software exists to map ortranslate data from and to XML for other data formats. This means thatUsers can store data in their internal systems in pre-existing formats,and still use the data to populate their GPM inputs without replicationor risk of inconsistency. Finally, XML is very flexible and extensible,allowing the creation of new data formats and data fields withoutimpacting pre-existing applications and systems. This capacity can beused, for example, to expand the range and scope of the GPM Systemwithout impacting the interfaces with payments applications.

Human interaction with the GPM System will use browser interfaces. Theuse of a browser interface has significant advantages: it will befamiliar to virtually all users of technology; it can be structured withcustomised “drop-down” lists for populating data fields for easy “pickand click” selection of counterparties, Third Parties, Users, PaymentBanks, currencies and other categories of data; and it can accommodatefree text messaging when appropriate. In particular, most recentinstances of browsers are capable of supporting eXtensible Mark-upLanguage (XML), the data format protocol selected for the illustrativeembodiment of the present invention, through the application of XSLstylesheets to the data. A further advantage of browser interface isthat the User Host Application and Payment Bank Host Application can beinstalled with a corporate information technology system, capable ofremote access from a plurality of geographically dispersed sites. Thiswill facilitate “passing the book” of payments risk management betweengeographically dispersed branches and offices, where a Payment Bank orUser wishes to actively manage and monitor payments activitiesworldwide.

As shown in FIG. 4, the GPM System of the illustrative embodimentcomprises a plurality of access devices and applications for Users (1),providing and receiving data to and from the GPM Core System by way of aplurality of internet protocol networks (6.2), which are interconnectedby way of routers (6.3) to the VPN (6.1) serving the GPM System. The VPNis then connected via router to the GPM Core System (2).

The GPM Core System in the illustrative embodiment comprises: aplurality of personal computers (e.g., IBM or similar) providing anOperations Workstation (2.1), Database Server (2.2), AuthenticationServer (2.3), Process Server (2.4) and Web Server (2.5), eachinterconnected to a Local Area Network (IAN) (2.6). A remote hot BackupSystem in the illustrative embodiment comprises a Backup OperationsWorkstation (2.7), Backup/Mirrored Database Server (2.8), Backup Process& Authentication Server (2.9) and Backup Web Server (2.10), eachinterconnected to a LAN (2.11). The GPM Core System and Backup Systemare via their respective LANs by bridges (2.12), in a conventionalmanner. The GPM Core System connects by way of the VPN (6.1) to thePayment Bank host applications (3) installed in the Payment Banks in theGPM System.

The User Host Application is optimally installed on a server within theUser's own internal back-office systems and accessed from a workstation,personal computer or network access device. The User Host Applicationwill usually be located at the User site principally associated withclearing and settlement of payments transactions, although it isunderstood that each instance of the User Host Application will promoteflexibility in User access, and may be networked via internal Usernetworks using conventional communication networking technology wellknown in the art.

In the illustrative embodiment, each instance of the User HostApplication at the User site supports a browser interface. Theparticular character of the browser interface may vary from embodimentto embodiment of the invention to flexibly adapt to the User'srequirements, complexity, various instances of the User HostApplication, and means of GPM Network access. However, it is preferredthat each such browser interface supports an array of display screensusing eXtensible Stylesheet Language (XSL) stylesheets which enablesHyper-Text Markup Language (HTML) representation of XML data anddocument type definitions (DTDs), and facilitates easy entry ofinformation by the User during the day, as well as displaying varioustypes of reports and notifications produced by the GPM Core System. (Itis noted that the invention could be realized at the User site tosupport a graphical user interface (GUI) using a GUI generator. In sucha realization, the installation at the customer site would operate as aclient on the server on which the User Host Application is installed.)The computers used to realize each instance of the User Host Applicationcan run virtually any type of operating system, such as the MicrosoftWindows NT operating system, Microsoft Windows 2000 operating system,earlier versions of the Microsoft Windows operating system, Unixoperating system, or the Macintosh operating system.

Each User Host Application instance cooperates with central serverprocesses operating on the GPM Core System Servers at the central siteby way of the data-packet network communication protocol supported overthe VPN, and interconnected internet protocol networks. The User HostApplication and GPM Core System will exchange data using anapplication-to-application interface.

In the illustrative embodiment, each instance of the Payment Bank HostApplication installed at the Payment Bank site supports a Filter ProcessModule which will interoperate in a modular manner with the pre-existingLiquidity/Payments Manager software already installed in the PaymentBank's legacy system for payments processing. The particular characterof the interface may vary from embodiment to embodiment of the FilterProcess Module to flexibly adapt to the Payment Bank's existing systemsand the interface requirements of the domestic payment system and/ormultiple payment channels.

Payment Banks will additionally have a browser interface to the PaymentBank Host Application for monitoring payment flows, Third Party and Userrisk parameters, inquiries, messaging and reports. This browserinterface will also be used to instruct manual override to enableparticular payments or to suspend payments to a particular counterparty,where this is deemed appropriate in the Payment Bank's discretion. Thecomputers used to realize each instance of the Payment Bank HostApplication can run virtually any type of operating system, as above forthe User Host Application. The browser interface and data structure forthe invention will support multiple languages and the global characterset used commonly worldwide. (It is noted that theapplication-to-application interface could be realized as an applicationclient on the client-server architecture of the GPM Core System, andthat the Payment Bank interface could be realized similarly with a GUI.)

In the illustrative embodiment, the processes of the present inventionin the GPM Core System are realized as client-server based processes,wherein the Process Server supports the server portion of the process,while a GPM Operations Workstation supports the client portion thereof.In order to realize such client-server processes upon the GPM CoreSystem, a data-packet network communication protocol is employed. TheGPM Core System uses a suitable network communications productcommercially available from a vendor of information bus technology(e.g., Tibco, IBM, etc.). The benefits of using a bus architectureinclude flexibility, extensibility, easier maintenance, improvedsecurity and the reinforcement of design goals such as modularity,abstraction and encapsulation.

All information items pertaining to Third Parties, Users, Payment Banksand parameters for processing in the GPM System, inquiries, messages andreporting, and the like are maintained within a database maintainedwithin the GPM Database Server (7). In the preferred embodiment, thisdatabase is realized as a relational database using commerciallyavailable database management computer software (e.g., Oracle, IBM).

In the illustrative embodiment, the virtual private network (VPN) (4)provides appropriately high levels of security and integrity for allcommunications across the GPM network using commercially availabletechnology for encryption, firewalls, anti-hacking measures, and assuredmessage and data delivery.

As shown in FIG. 5, the GPM System will use a system of digitalcertification to ensure the security of network access against use orinfiltration by unauthorised persons. A digital certification process,commercially available from several digital certification authorities,will be used to issue digital certificates to all remote hostapplications and to ensure their use whenever any remote hostapplication accesses the GPM Core System at the initiation of a session.

In addition, all transmissions via the GPM Network will be digitallyencrypted using security technology suitable for high security bankingapplications.

As shown in FIG. 6, the GPM System of the present invention will greatlyalter the risk profile attaching to foreign exchange settlements, butwith relatively minor impact on conventional processes used byparticipants and their branches or correspondent banks (collectively“Payment Banks” for GPM). On the Trade Date, the dealing, confirmation,matching and payment instructions continue as before. But following thegeneration of payment instructions, the GPM User Host Application willallow a User to construct a profile of their payment risk in eachcurrency vis-a-vis each market counterparty. Using this software andtheir own discretion regarding the tolerance of their institution forcredit risk on each counterparty, the User can generate a file ofpayment risk parameters to control the payment risk by Counterparty,currency and payment type. The parameters for each counterparty can beset differently for each currency for which GPM operates (e.g., $100 Min US dollar, as a very liquid currency, but only $10 M in MalaysianRinggit, as a relatively illiquid currency). The parameters can also beset according to payment type in accordance with the definition ofpayment message types by S.W.I.F.T. and the various alternative domesticpayment systems (payment channels).

On the Settlement Date, the Payment Bank constructs the payment queue ofpayment messages for that date. The GPM Filter Process Module is amodular software component acting in a complementary manner to existingliquidity and payment queue management software interfacing to thedomestic payment system. As before, the Liquidity/Payment Managerassesses whether sufficient liquidity exists in the clearing accountwith the domestic payment system to enable an outgoing payment. If thepayment passes the Liquidity/Payment Manager, then the payment isadditionally submitted to the GPM Filter Process Module. This moduleassesses the payment message against the parameters set by a Third Partyand/or User for the counterparty/recipient to see whether the parameterswill be violated by the outgoing payment. If no, then the payment isreturned for processing to the interface with the domestic paymentsystem as usual. If yes, then the payment is returned to the back of thepayment queue for further assessment next time it comes up in the queue.

Payment Banks will generate S.W.I.F.T. MT900 and MT910 messages asbefore. These messages and/or the data underlying their generation willbe used to populate the metrics controlling the assessment of paymentsagainst the Available Balance calculated in the Filter Process Module.In particular, the Payor designation, Payee designation and the amountsof debits and credits will be extracted from the messages as data fieldsand used to update the Available Balance metric for the relevantcounterparty and User/Third Party.

The Payment Bank Host Application will be capable of issuingnotifications as exceptions conditions arise. For example, where allpayments to any Counterparty are rejected for a half-hour period (orother appropriate timespan), a notification may be issued to both thePayment Bank and the Third Party and/or User to apprise them of thesustained failure. On receiving this alert via the GPM network, theThird Party and/or User can make appropriate inquiries immediately.Where no substantial problem exists with a counterparty, a Third Partyand/or User may request via the GPM network that the Payment Bankmanually override Filter Process Module to enable payments to proceed.

If the Third Party and/or User has cause for real concern, however, hecan suspend further payments the counterparty via the GPM Network. Amechanism for suspension of payments will result in the Filter ProcessModule rejecting any further payments for the counterparty, and may beeffected for all currencies for which the participant uses the GPMSystem in one simple and efficient instruction. The early detection of acounterparty payment failure will also reduce the systemic impact ofdefaults by enabling a participant of the GPM System to calculateexactly his payment exposure to a counterparty, and to fund morereliably any shortfall (necessarily limited to the Clean Payment Limitparameter) in liquidity which might affect his own ability to makecontingent payments in affected currencies.

An inquiry to determine the Available Balance for the Counterparty atall Payment Banks will give the participant a precise measure of anypayment exposure he has vis-a-vis the Counterparty. Because theAvailable Balance is updated in real-time as payments are made, itprovides very precise information on the Counterparty exposure andliquidity impact of a default.

On a day-to-day basis the User can monitor his credit exposure acrossall currencies in respect of a particular counterparty both periodicallyand on-demand in a much more efficient and reliable manner. The GPMSystem and User Host Application will enable flexible aggregation ofpayment flows to provide better information to support risk managementand trading decisions vis-a-vis counterparties. When combined with thelimits on payment risk operating in the GPM System, the effect should beto increase the global capacity for trading volumes by reducing thepresent credit constraints which arise due to gross payment exposures.

There may be occasional situations in which a Payment Bank might wish tooverride the automated risk parameters of the Payment Bank HostApplication to permit a payment to proceed, despite its non-compliancewith risk parameters set by the User. In this event, an overridefacility is provided whereby the Payment Bank can permit individualpayments to proceed for payment despite the breach of risk parameters.

On the Reconciliation Date, the Users will use the MT950s generated asusual by Payment Banks for reconciliation in their existing processes,with no change to conventional practices. They can follow up on failedsettlements of individual transactions accordingly, but the advantage oflearning of the amounts of payments not received on the day previousshould eliminate much of the stress and uncertainty attendant on theprocess using prior art systems and techniques.

As shown in FIG. 7, the GPM System is backward compatible with existingmessaging, payments and risk management processes within marketparticipants and payment banks. The GPM System supplements the currentinfrastructure by providing a logical flow of information betweenaccount holders and payment banks to improve the functionality ofpayments control and also communications between banks and accountholders. In the illustrated schematic, the User receives confirmation ofmarket transactions (A) from the S.W.I.F.T. network. The transaction ismatched (B), and the payment instructions are generated (C) and sent (D)via the S.W.I.F.T. network to the Payment Bank (E). At the Payment Bank,the payment instructions are lodged in a forward payment instructionscache (F) until the payment date. The User then forwards the informationabout payments exposures to his risk management operations. The riskmanagement operations will determine appropriate levels of risk exposureto the counterparty according to tolerance for counterparty credit risk,currency liquidity risk and other measures (G). The resulting riskparameters are entered (H) in the module for generating risk parametersand suspend instructions in the User Host Application (1.1). The UserHost Application communicates these risk parameters to the GPM CoreSystem (I), which applies rules-based processing (J) and data storage,and forwards the risk parameters (K) to the Filter Process Module in thePayment Bank Host Application via application-to-application datainterchange.

On the payment date, a queue of all pending payments messages isconstructed from the stored payment instructions (L). As paymentsoperations commence, each payment message is forwarded to the paymentsor liquidity management software controlling payments sent to thedomestic payment system (M). If the payment fails the parameters in thisprocess, it is returned to the queue (N). If it passes, then it isforwarded to the Filter Process Module cooperating with the existingpayments or liquidity management software (O). The Filter Process Moduleassesses the payment against the risk parameters for thecounterparty/recipient (P). If it fails, the payment message is returnedto the payments queue (Q). If it passes, the payment message isforwarded (R) to the domestic payment system for payment (S).

Data regarding incoming payments are captured to populate the AvailableBalance metrics essential to the Filter Process Module (T).

Notifications, messages, inquiries and reports can flow between the Userand the Payment Bank via the GPM System in an automated or on-demandbasis. In the illustration, the Payment Bank may generate a notification(U) which is sent (V) via the Core System messaging facility (W) andrelayed (X) to the User Host Application for notification (Y) of theUser. All message traffic is stored for audit purposes (Z).

As shown in FIG. 8, the GPM System of the present invention enablespayments to be randomly sequenced as between two counterparties so thatno great imbalance in credit exposure occurs between them. Payments arereleased by the Filter Process Module up to the Clean Payment Limit, asdetermined by the Third Party or User. Following that, further paymentsto the same counterparty will be filtered and returned to the paymentsqueue. Only when receipts of expected payments from the Counterparty arecredited to the User's account (designating either the User or a ThirdParty as beneficiary) will further payments be released. In this manner,the Filter Process Module ensures the regularity and moderation ofpayment flows between two parties.

Only one party needs to be a User or Third Party for the GPM System toprove effective. The ability to control risk without the expressagreement or cooperation of a counterparty is a significant innovation.

As shown in FIG. 9A 1, the Third Parties and Users accessing the GPMSystem will generate and send instructions (A and B) to their PaymentBanks (branches and banks making payments on their behalf into domesticpayment systems) to control the payments against risk parameters. Theserisk parameters are designed to control the level of payment risk andliquidity risk arising in connection with a Counterparty. The ThirdParty Host Application (4) will be capable of generating riskparameters, but will not have direct access to the GPM System. The ThirdParty must therefore forward its risk parameters to a User acting on hisbehalf (A). The User Host Application (1) can generate risk parameterson behalf of the User and Third Parties, and send these, as well asrelaying any Third Party risk parameters, to the GPM Core System (B).The GPM Core System (2) will analyse and sort received data files usingrules-based processing. Data will be stored, and also forwarded todesignated recipients. Risk parameters will be forwarded to the PaymentBanks (C) designated as making payments on behalf of Users and ThirdParties. The Payment Bank Host Application (3) will store received riskparameters and apply them during the Filter Process (D). Only paymentinstructions passing the parameters in the Filter Process will beforwarded to the Domestic Payment System (5) for payment (E).

As shown in FIG. 2A 2, the risk parameter instruction generated by theThird Party or User Host Application will contain a variety of datarelevant to the routing and application of the risk parameters. The dataformat fields follow content standards defined by S.W.I.F.T. for paymentmessages, and so will be backward compatible with existing paymentprocessing systems and industry conventions. Although the data ispresented here in the format of an industry standard message, the datain the Third Party or User Host Application will be generated using aflexible browser interface, allowing easy and transparent selection ofcounterparties, currencies, payment types. It will be captured in theformat of an XML document type definition (DTD) suitable for thestructure of data, and in particular the need for flexibility in thecharacterisation of counterparties. The representation here indicatesthat there can be multiple counterparties designated as subject to asingle risk parameter. This will be particularly useful for aggregatingaffiliated branches or corporate entities which are likely to bemutually implicated in a default or insolvency. In this manner, a Useror Third Party can control risk in a manner tailored to his perceptionof correlation among affiliated or similar trading entities. Therepresentation also permits multiple categories of Payment Type,recognizing that Users or Third Parties may wish to be selective inapplying GPM processing to particular categories of payments oralternative payment channels.

As shown in FIG. 9B, the Risk Parameters operating in the Filter Processare quite simple, consisting of the Counterparty (however designated oraggregated), the Clean Payment limit, and designation of Payment Types.These three parameters are sufficient to enable the Filter Process tocontrol the payment risk and liquidity risk arising in connection withthe Counterparty for all payments of the designated types.

As shown in FIG. 9C, the Filter Process Module in the Payment Bank HostApplication is intended to co-operate and be backward compatible withthe existing liquidity and/or payments management software controllingthe outflow of payments instructions to the domestic payment system.Liquidity/Payment Managers are software typically designed to evaluateindividual payments messages against (a) the available balance overallfor the bank in the domestic payment clearing account (generally anaccount held at the central bank for a real-time gross payment system),and (b) the available balance in the account of the account holderreferenced in the payment instruction (the account to which a debit willbe made for the payment). If a payment instruction fails either check,it is rejected back to the payments queue for re-evaluation later. Wherea payment instruction clears these two parameterized evaluations, it isforwarded for payment through the gateway to the domestic paymentsystem.

The Filter Process Module in the Payment Bank Host Application will be amodular extension of the parameterized evaluation already operating inthe Liquidity/Payments Manager. Using an application-to-applicationinterface which translates the data formats of the liquidity/paymentsmanager to the data formats of the Filter Process Module, and backagain, the two application modules can interoperate without retooling ofthe existing application. Payments clearing the assessments of thelegacy Liquidity/Payments Manager will be forwarded to the FilterProcess Module for assessment. If they fail such assessment, they arereturned to the queue as before. If they pass, they are forwarded to thegateway to the domestic payment system as before. This modularintegration with existing systems offers backward compatibility,providing lower integration costs and widespread adaptability of the GPMprocess.

As shown in FIG. 2D 1 and 2D2, the Filter Process Module operates alogical algorithm for assessment of payments instructions. The processassumes that a payment instruction has been transmitted from theLiquidity/Payments Manager application within the Payment Bank's systemsto the Filter Process Module for evaluation. As shown in FIG. 2D 1, StepA of the Filter Process involves is to identifying the Payor on thepayment instruction message. This will be possible using industrystandard fields (e.g., Field 52A for an Ordering Institution, Field 50for an Ordering Customer, or similar designations as pertain to domesticpayment systems).

Step B of the Filter Process involves assessing whether the Payor is aUser or Third Party using the GPM System. If NO, then the paymentinstruction is passed back to the liquidity/payment manager fortransmission to the domestic payment system interface without furtherevaluation. If YES, then the Filter Process Module proceeds to Step C,identifying the Payee. The Payee will be the beneficiary of the paymentinstruction. This is designated using industry standard fields (e.g.,Field 59 for a Beneficiary Customer, designated as the ultimaterecipient of the funds being transferred).

Step D of the Filter Process involves assessing whether the Payee is adesignated Counterparty as defined in received risk parameters. If thePayee identified is not a Counterparty for granular payments management,the payment instruction is passed back to the liquidity/payments managerfor processing to the domestic payment system. If the Payee is acounterparty as defined in the risk parameters, then the Filter ProcessModule goes to Step E to determine whether the counterparty is suspendedfrom further payments. If the Payee has been suspended, then allpayments instructions will be rejected back to the payments queue untilsuch time as the suspension may be lifted.

At Step F, the Filter Process Module identifies the payment type of thepayment instruction under analysis. The default will be to subject allpayment types to the Filter Process unless only specific payment typeshave been designated for processing. Thus if the payment type (e.g.,MT200 or MT202) has been specifically designated for processing in therisk parameters (an optional specification) then it will be passed toStep F. If it has not been so designated, it will be passed back to theliquidity/payment software for further processing to the payment system.

This step can also be used to differentiate payment channels where thereare more than one domestic payment systems. For example, the UnitedStates has two large value payments systems: Fed wire operated by theFederal Reserve System, and the Clearing House Interbank Payment System(CHIPS), operated cooperatively by the New York Clearing HouseAssociation. The payment type identifier in the risk parameters can bestructured to reference the various payment channels (as alternativepayment systems are known), so that, for example, payment instructionsfor Fed wire would be subjected to the Filter Process but paymentinstructions for CHIPS would not. (Where separate liquidity/paymentsmanagers operate for separate payment channels, the Filter ProcessModule could be installed in multiple instances within the Payment Bank,achieving the same objective.)

Where the payment instruction is eligible for the Filter Process at StepG, the Filter Process identifies the payment amount from the paymentinstruction at Step H (e.g., Field 32A on a S.W.I.F.T. message type).

Step I of the Filter Process Module involves calculating the AvailableBalance for the counterparty. This involves a process explained fullybelow.

Step J of the Filter Process involves comparing the Available Balanceagainst the payment amount. Where the Available Balance exceeds thepayment amount, the payment instruction is passed back to theliquidity/payments manager for further processing. Where the paymentamount exceeds the Available Balance, the instruction is rejected backto the payments queue, and the liquidity/payments manager notifiedaccordingly.

Finally, at Step K of the Filter Process, the Available Balance isreduced by the amount of any payment and stored.

As shown in FIG. 9E 1 and FIG. 9E 2, the Available Balance is calculatedusing a logical algorithm with seven steps. Step I.1 is to identify theUser or Third Party (as done in Step A of the Filter Process). Step I.2is to identify the Counterparty (as done in Step B of the FilterProcess). Step I.3 is to identify the stored Available Balance. Thisamount will be either (a) the Clean Payment Limit at the beginning ofpayments processing for the day, (b) the stored Available Balance asrevised during Step K of the Filter Process, or (c) the stored AvailableBalance as revised by receipt of amended Risk Parameters specifying achange to the Clean Payment Limit.

At Step I.4, the process for calculating the Available Balance sends atimestamped inquiry to the payments/liquidity manager or otherappropriate application to determine whether incoming payments have beenreceived designating the User or Third Party under consideration as abeneficiary since the last timestamped request. If so, the amounts ofany such payments are totaled (Step I.5) and added to the AvailableBalance (Step I.6). The recalculated Available Balance is stored andforwarded (Step I.7) to the Filter Process in fulfillment of Step I ofthat process.

As shown in FIG. 9F 1, the same process used for generating and sendingrisk parameters can also be used to generate and send instructions tosuspend all payments to a particular Counterparty. The GPM System willenable a User (or Third Party via a User) to suspend all furtherpayments to a designated Counterparty in one, several or all currencieswith an instantaneous instruction. The Third Party (4) or User HostApplication (1) initiates the process of suspension. Using the browserinterface to the host application, the User or Third Party selects theCounterparty (from a drop down list), selects the currencies for whichsuspension is sought (from a drop down list) and then clicks on a buttongenerate a Suspend Instruction. The application will ask the User orThird Party to confirm the instruction according to its terms as aprecaution appropriate to so serious an intervention in the paymentsprocess. Where the Suspend Instruction is confirmed, it is sent via theGPM Network to the GPM Core System (Step A on FIG. 9F 1).

The GPM Core System identifies, Payment Banks for receipt of the SuspendInstruction acting for the User in the affected currencies. The CoreSystem then routes the Suspend Instruction via the GPM Network to thePayment Bank Host Application (3) (Step B on FIG. 9F 1). The PaymentBank Host Application sets the trigger in the Filter Process todetermine that the Counterparty has been suspended (Step C on FIG. 9F1). When a payment instruction for the Counterparty comes through theFilter Process, it will be rejected and returned to the payments queue(Step Eon FIG. 9D 1 and FIG. 9D 2). As a result, no payments for thatCounterparty will be permitted until the trigger is reset to remove thesuspension (in the event the Counterparty is reinstated).

Once the trigger in the Filter Process has been set to Suspended for aCounterparty, the Payment Bank Host Application generates an automatednotification to confirm implementation of the Suspend Instruction (StepD on FIG. 9F1). The notification is passed through the GPM Core Systemback to the User (Step E) and Third Party, if any (Step F), where theconfirmation of the Suspend Instruction is notified as an alert andstored.

The process of the present invention described hereinabove represents avery important advance in the control of payments risk during a defaultcrisis. In many countries, the legal system applying in bankruptcyallows for the unwinding of payments which are made after an insolvencypetition is filed or, in some countries, all payments occurring on thedate of an insolvency from midnight onwards. As a result, the unwindingprocess can result in great dislocation to payments systems, resultingin unquantifiable payments risk, liquidity risk and systemic risk. Theearlier a party to a transaction can intervene to prevent furtherpayments, the better. The GPM System presents a significant innovationin enabling a participant to suspend payments in all currencies for acounterparty from the moment he first learns of a default or insolvencysituation, while at the same time allowing the participant to knowexactly the extent of his payment risk and liquidity risk in eachcurrency (the Clean Payment limit).

The Suspend Instruction will remain a bar to all further payments in theFilter Process until processing is reinstated. Reinstatement is achievedby the simple mechanism of sending a new Risk Parameter Instructionreferencing the suspended Counterparty. When received by the FilterProcess, the suspension trigger is reset and the new risk parameters areimplemented in Filter Process logic.

As shown in FIG. 9F 2, the Suspension Instruction message fields willsimply identify the Third Party and/or User originating the SuspendInstruction, the Payment Bank addressed by the Suspend Instruction, theCounterparty suspended, and the nature of the instruction as a SuspendInstruction.

As shown in FIG. 9F 3, the steps alluded to in FIG. 9F 1 can be detailedwithin the process for the Third Party or User Host Application, the GPMCore System and the Payment Bank Host Application. Together, theprocesses provide an effective and secure means of rapidly suspendingpayments to a Counterparty where there are reasonable grounds forfearing that the Counterparty is insolvent or otherwise incapable ofperforming his obligations.

Method of Using the GPM System of the Present Invention

Having described the illustrative embodiment of the GPM System hereof,it is appropriate at this juncture to describe a preferred method ofusing the same.

Opening an Account with GPM

Each entity involved in the GPM System, whether User, Third Party,Payment Bank or Counterparty will have a Unique Identifier (UID). ForPayment Banks and many Users, this will be their BIC code. Other Usersand Third Parties may have a unique industry standard identifier ofanother sort, which can be used by the GPM System. Otherwise, the GPMSystem will issue its own unique identifier in a format analogous to theBIC code. The unique identifier will enable the GPM System to track anentity's involvement in the system, regardless of the nature of its rolein any particular system action.

Users

Each User will have at least one account within the GPM System. Eachaccount can support one or more User or Third Party identities, or acombination thereof. Users may flexibly identify themselves, affiliatesor others as Users or Third Parties such that various hierarchies ofcorporate affiliates, branches, clients and other sub-groupings areseparately accounted for within the GPM System.

Users may reflect their organizational and administrative hierarchy byidentifying Users or Third Parties as they choose, including providingclient identifiers used in their internal systems, and may createvarious account hierarchies for aggregation or disaggregation of riskmanagement and reporting.

In the illustrative embodiment, Users will seek to open an accounton-line via a Website maintained on the World Wide Web or other Web(s)by the GPM System. If accepted on review, the GPM System willautomatically issue account identifiers to Users as accounts are openedin the system. GPM operations personnel shall issue, modify and managecustomer account creation, deletion and security features, includinguser logins, passwords, and authorisation verification procedures inconnection with access privileges for each employee within a User.

In addition, the GPM System will make use of global digitalcertification. Each User will require issuance of a digital certificateas part of the User acceptance process. Each session with the GPM Systemthereafter will begin with verification of the digital certificatedetails with the digital certification authority.

The GPM System will identify each User or Third Party accountseparately, but many Users may wish to aggregate an account hierarchy topromote more efficient liquidity and/or risk management in connectionwith their payments activities. Users may elect to create one or more“synthetic” accounts representing an aggregation of User and/or ThirdParty accounts. By way of example, a foreign exchange dealer may wish tocreate individual Third Party accounts for each client for which thedealer acts in negotiation and settlement of foreign exchangetransactions. However, in order to manage his liquidity and paymentsrisk across the range of client accounts, he may elect to aggregate theaccounts into a single master account.

User details necessary for the management and billing will be stored onthe GPM Data Server. These details will include, but are not limited toaccount name, company name, contact name, address, telephone number,facsimile number, e-mail address, account number, billing information,and communication information.

All User access will be protected through a User-basedaccess/entitlement security mechanism including digital certification.Only properly authorised Users will have the ability to instigate GPMSystem actions, including creating and modifying Third Party, User andcounterparty details, entering or modifying Net Payment limits, enteringor modifying Risk Parameters, instructing Suspend Instructions forsuspension of further payments, and creating or altering report formats,or generate messaging, inquiries, and other system actions.

On an ongoing basis, the GPM System maintains records of User access andusage of the GPM System, and Users will have access to these records byway of inquiry and report facilities.

Payment Banks

Each Payment Bank will have at least one account within the GPM System.A Payment Bank account will be identified by its BIC code, although thesame entity may have other accounts as a User. Banks may have multipleaccounts as Payment Banks so long as each is associated with a differentBIC code (e.g., where the bank has branches participating in differentdomestic payment systems worldwide).

GPM operations personnel shall issue, modify and manage Payment Bankaccount creation, deletion and security features, including user logins,passwords, and authorisation verification procedures in connection withaccess privileges for each employee within a Payment Bank.

Payment Bank connection to the GPM System will also make use of globaldigital certification. Each Payment Bank will require issuance of adigital certificate as part of the acceptance process. Each session withthe GPM System thereafter will begin with verification of the digitalcertificate details with the digital certification authority.

Payment Bank details necessary for the management and billing will bestored on the GPM Data Server. These details will include, but are notlimited to account name, company name, contact name, address, telephonenumber, facsimile number, e-mail address, account number, billinginformation, and communication information.

All Payment Bank access will be protected through a Payment Bank-basedaccess/entitlement security mechanism including digital certification.Only properly authorised Payment Bank employees will have the ability toinstigate GPM System actions, including management of Userrelationships, creating or altering report formats, and generatingnotifications, messaging, inquiries, and other system actions.

On an ongoing basis, the GPM System maintains records of Payment Bankaccess and usage of the GPM System, and Payment Banks will have accessto these records by way of inquiry and report facilities.

Creating Counterparty Risk Parameters Within the GPM System

Counterparties can be any entity with whom the User or Third Party hasregular payments flows. Where a counterparty is not itself a participantin the GPM System, the counterparty will nonetheless be identified tothe system by its BIC or UID.

The definition of counterparties will be an important element in riskcontrol, as affiliated entities might be aggregated as a singlecounterparty for risk management purposes, even where each entity tradesfor its own account (e.g. geographically diverse branches of a singlebank). The User will be able to define a counterparty for its ownpurposes as an aggregation of UIDs and/or BICs.

The GPM System of the illustrative embodiment facilitates flexibility increating and modifying counterparty risk parameters for use in the GPMSystem. Where a User elects human interaction, he can manually enterRisk Parameters via a browser interface to the User Host Application.Alternatively, he may translate a spreadsheet file into a fileconsistent with User Host Application formatting requirements. For fullyautomated processing, the User may have an application-to-applicationinterface which automatically generates counterparty risk parameters forthe GPM System from data and processes in his internal back-officesystems.

Where a User is setting counterparty risk parameters, manually, theywould select a counterparty from a drop-down list on the screen (with anoption to add a new counterparty). On the next screen they would bepresented with a table of currencies (with an option to add or deleteparticular currencies) and spaces for Clean Payment Limit.

The User can set counterparty parameters either by sending an individualinstruction for a counterparty on-line, or by way of file upload at anytime during a session.

Instances of the User Host Application for application-to-applicationinterface may include a periodic automated initiation of connection tothe GPM Core System with fully automated upload of data files for riskparameters.

GPM Filter Process Module Processing

The GPM System stores received data and messages from Users in the GPMCore System Data Server. The data and messages are validated for syntaxand field validation. The Process Server then analyses the data, sortingcounterparty instructions in the first instance according to the BIC ofthe Payment Bank. The data is then compiled for transmission to thePayment Bank Host Application.

The Payment Bank Host Application is configured to accept counterpartyrisk parameters as parameters for rule-based decisions in the FilterProcess Module on whether to permit individual payments messages toproceed for payment to the domestic payment system or return the paymentmessage back to the payment queue held on the Payment Bank's internalsystems. Where a payment complies with risk parameters, it will beallowed to proceed for payment. Where a payment would breach theparameters, it is returned to the payment queue for later reassessment.

The Filter Process Module is acting in real-time to control User riskvis-a-vis the counterparty. It does this by using the data captured fromincoming payments from the counterparty and outgoing payments to thecounterparty to update the Available Balance calculated within theFilter Process Module about payment flows. Payments from a counterparty(e.g., reflected in the generation of an MT 910) add to the AvailableBalance for outgoing payments. Outgoing payments (e.g., reflected in thegeneration of an MT 900) detract from the Available Balance. Because thepayments messages use standard data formats and identifiers for banksand account holders, these data fields can be captured and interpretedconsistently to populate the calculations in the Filter Process Modulein conformity with a large number of domestic payment systems.

The Payment Bank Host Application will maintain a log of paymentsactivities. This will enable flexible compilation of reports on either aperiodic or on-demand basis. At the end of the day, summary informationabout the day's activities will be transmitted to the GPM Core System aspart of the log-off process.

Exceptions Processing

Where the Payments Bank Host Application has rejected payments to aparticular counterparty for some pre-defined period of time (e.g.,half-hour), it will automatically generate a notification to alert thePayment Bank and the User to the potential problem. Either or both maythen request a report of payments activities concerning the counterpartybe generated by the Payment Bank Host Application.

Very often a User will want to initiate inquiries with a counterpartywho has failed to make timely payment as expected. If the counterpartyis also a User or Third Party within the GPM System, the User receivingan exception notification can initiate an inquiry through on-linemessaging to the User or Third Party. (Third Party messaging will berouted through the Third Party's designated User.)

Overriding Payments Filter

There may be instances where a Payment Bank will wish to override thePayments Bank Host Application to enable a payment to proceed to thedomestic payment system despite its failure to pass all risk parameters.If so, the Payment Bank will access the Payment Bank Host Applicationvia a browser interface. It will identify the payment it wishes to acton from the log of rejected payments. It can then instruct the FilterProcess Module to override the parameters for that payment the next timeit is processed, enabling the payment to go forward to the domesticpayment system.

Suspending a Counterparty

If on investigation the Third Party or User is inclined to believe thata counterparty is in difficulty and at risk of default, or indeed issubject to an insolvency action, the Third Party or User may wish tosuspend further payments in order to reduce any credit exposure to thecounterparty. To do this the Third Party or User will access the browserinterface for the Third Party or User Host Application, bring up thecounterparty from a drop down list, and click on a button for “suspendpayments”. This button will lead to a screen displaying all thecurrencies dealt with for that counterparty. The Third Party or Userthen has the option of selecting individual currencies or pressing abutton for “select all”. Once the currencies are selected according tothe User's discretion, he will click a button labeled “send SuspendInstruction”. He will be asked to confirm whether he really wants tosuspend further payments to the counterparty, with a yes or no option.If he clicks the “yes” button, the instruction to suspend payments willbe sent to all Payment Banks acting for the User.

When the Payment Bank Host Application receives a Suspend Instructionreferencing a counterparty, the Filter Process Module will automaticallyengage a trigger to reject further payments messages, regardless ofcompliance with risk parameters. The Payment Bank Host Application willgenerate a notification to the Payment Bank of the implementation of aSuspend Instruction. The Payment Bank still has the discretion tooverride the Payment Bank Host Application to release individualpayments should it determine to do so despite the effectiveness of theSuspend Instruction.

Inquiries, Reports and Messaging

Risk reduction and control are enhanced in the GPM System by theprovision of flexible real-time and periodic mechanisms for inquiries,reports and messaging. Any participant in the GPM System (Third Party,User or Payment Bank) will be able to send messages to any otherparticipant in real-time, using standard e-mail capabilities integratedinto the GPM System. Inquiries can be structured as automated processeswhere the data sought by a User or Payment Bank can be obtained in anautomated manner from the Payment Bank Host Application. Reports toparticipants on GPM System usage will be generated on an on-demand andperiodic basis covering a variety of parameterised matters. These arelikely to include: counterparty gross payments total, counterparty riskparameters, GPM risk reduction metrics, liquidity and efficiency ofpayments metrics, and other matters determined by the participants to beof interest. Participants will be able to structure reports to aggregatea variety of User accounts, Third Party accounts and counterparties, asrequired to form a consolidated view for their own risk management andregulatory reporting needs.

Audit Trail

The GPM System will maintain a comprehensive audit trail within the GPMCore System Data Server of all system actions such that all actions canbe reviewed for audit, regulatory and recovery purposes. The GPMOperations Workstation will be able to access the audit trail via theoperator's browser interface to the system.

Advantages of the Present Invention

As shown in the graph of FIG. 10, the GPM System of the presentinvention provides simple and effective risk reduction with greatadvantages over all prior art systems hitherto known. The accompanyinggraph is an illustrative example of the effect of risk management asbetween two market counterparty Users of the GPM System of the presentinvention (although only one needs to use GPM for it to be effective).In this example, Party A and Party B have entered into a plurality oftransactions throughout a trading day resulting in a portfolio oftrades. The graph shows the gross amounts which must be paid insettlement of these trades such that Party A must pay $55 M worth of USdollars and $45 M worth of Euro at market prices. Party B must pay $55 Mof Euro and $45 M worth of US dollars to settle its gross obligationsunder the same portfolio of transactions. (All amounts are measured inUS dollars for convenience of reference.) As a result, each party mustpay the gross amount of $110 M. In the current system, payments to thisamount would be made without any assurance of receiving thecounterpayments of $110 M value expected from the counterparty to thetransactions. As a result, each party would undertake payment risk andliquidity risk of $110 M on the other for that day's settlements.

Under the GPM System of the present invention, however, each party setshis own Clean Payment Limit for each currency. In this example, Party Ahas set the Clean Payment limit in US dollars at $10 M, while Party Bhas set it lower at $3 M. Party B's risk on Party A is therefore lowerthan Party A's risk on Party B, consistent with individual riskassessment and the extent of the payment obligations. In Euro, Party Bhas set his Clean Payment limit at $10 M, consistent with his netpayment obligation, and Party A has set his Clean Payment Limit at $2 M,perhaps reflecting the greater difficulty of financing liquidity in Eurorather than a poor assessment of Party B's credit. The total paymentrisk for each party is reduced to their net payment obligation in thesold currency and the Clean Payment Limit in the bought currency. (Thereal measure may well be substantially less if the amount of the NetPayment limit has been offset by receipts of payments in other paymentsystems in earlier time zones prior to a default.) In the illustratedexample, the gross payment risk of $110 M has been reduced to $12 M forParty A and $13 M for Party B.

The amounts set for Clean Payment limits are within the discretion ofThird Parties and Users, but some guidance and good practice are likelyto emerge relatively quickly. As a rule, the Clean Payment Limit shouldequal or exceed the greater of the net payment amount in a currency (ifany) or the single largest gross payment. If participants follow thisguidance, then the GPM System will promote improved liquidity inpayments systems by ensuring that payments liquidity flows to thosemaking payments in a timely and sensible manner.

Other Uses and Modifications

Many aspects of the present invention relate to participant interfacetechniques for generating, storing, accessing and communicatinginformation. data or messages which need not relate solely to paymentsor even financial transactions alone, but could relate to the controlledor balanced allocation of other resources.

While the illustrative embodiment of the GPM System described above willhave many applications to the financial industry, it is understood thatvarious modifications thereto will occur to those with ordinary skill inthe art. However. all such modifications and variations are deemed to bewithin the scope and spirit of the present invention as defined by theaccompanying claims to Invention.

1-12. (canceled)
 13. A method of reducing payments risk, liquidity risk,and systemic risk in a system supporting a plurality of Third Party HostApplications, a plurality of User Host Applications, and a plurality ofPayment Bank Host Applications, each said payment Bank Host Applicationhas a Filter Process Module for processing payments instructions, saidmethod comprising the steps: (a) said Third Parties sending counterpartypayments risk data to said Users associated with a plurality ofpayments-based transactions; (b) said Users sending counterpartypayments risk data on behalf of themselves and said Third Parties tosaid system, wherein said payments risk data specifies transactionparameters selected from the group consisting of (i) the User associatedwith each said payments-based transaction, (ii) the Third Partyassociated with each said payments-based transaction, (iii) the PaymentBank associated with each said payments-based transaction, (iv) theintermediary(ies) in the chain of accounts leading to the counterpartyor ultimate payment beneficiary, (v) the counterparty associated witheach said payments-based transaction, (vi) the currency associated witheach said payments-based transaction, (vii) the payment type associatedwith each said payments-based transaction, (viii) the TransactionReference Number unique to each payment transaction, and (ix) the CleanPayment Limit associated with each said payments-based transaction; (c)said system analysing the payments risk data associated with each saidpayments-based transaction and decomposing said payments risk data intofiles for transfer to said Payment Bank Host Applications makingpayments on behalf of said Users in a plurality of currencies; (d) saidsystem transmitting said payments risk data, associated with each saidpayments-based transaction, to said Payment Bank Host Applications,using application-to-application automated interfaces; and (e) each saidPayment Bank Host Application applying said payments risk data as inputparameters to said Filter Process Module for automated evaluation ofpayments instructions in respect of accounts of said Users such thatpayments instructions breaching said input parameters to said FilterProcess Module are rejected back to a payments processing queue forlater re-evaluation in the absence of an override instruction.
 14. Themethod of claim 13, wherein each Third Party, User and Payment Banksending payments risk data can also generate and receivepayments-related notifications, inquiries, messages and reports viatheir respective host applications.
 15. The method of claim 13, whereinsaid Filter Process Module within each said Payment Bank HostApplication cooperates with payments processing with said domesticpayment system operated by said Payment Bank, such that paymentsinstructions are filtered by said Filter Process Module for compliancewith suspend instructions, override instructions and payment riskparameters.
 16. The method in claim 14, wherein each Third Party andUser can request and receive reports from a plurality of said PaymentBanks acting on their behalf.
 17. The method of claim 13, wherein eachsaid Payment Bank Host Application capable of calculating the AvailableBalance for counterparty payments through incorporation of datainterchange with existing payments confirmation services and monitoringelapsed time.
 18. The method of claim 14, wherein each Payment Bank HostApplication can generate a notification to the Payment Bank and Userand/or Third Party in the event that a counterparty fails to makeexpected payments for a pre-determined period of elapsed time and detailpayments which have failed to pass the Filter Process according to theirTransaction Reference Numbers.
 19. The method of claim 18, wherein eachThird Party or User receiving notification of a counterparty paymentfailure may instruct Payment Bank suspension of further payments to saidcounterparty or instruct override of the Filter Process to allowindividual identified payments to proceed or allow payments to specifiedcounterparties or intermediaries.
 20. The method of claim 17, whereineach Payment Bank Host Application will automatically incorporate asuspension of all further payments to a counterparty on receipt of anotification to do so via implementation as a trigger in the FilterProcess Module and incorporate overrides as instructed.
 21. The methodof claim 13, wherein each Payment Bank and User are subjected to digitalcertification to establish their access authority and usage constraints,and wherein data transmissions are encrypted for security purposes. 22.The method of claim 13, wherein Third Party, User and Payment Bank hostapplications are human-accessible by browser interface andmachine-accessible by incorporation and translation of electronic datainterchange formats.
 23. The method of claim 13, wherein Third Partiesand Users can flexibly identify counterparties by means of aggregatingidentifiers unique to individual corporate or organizational entities,creating thereby synthetic counterparties composed of entities deemed toshare correlation in payment risk assessment.
 24. The method of claim13, wherein said system further comprises Core System Host Applicationfor recording various type of information, including identification ofsaid Users, identification of said Third Parties, identification of saidPayment Banks, identification of said counterparties, identification ofcurrencies, specification of the Clean Payment Limit (Debit Cap), anyoverride instructions, and Payment Type identification, includingalternative payment channels, if any. 25-56. (canceled)